Add support for inheritance #129
Conversation
Config format is refactored so that entries reflect which pipeline steps they belong to. Pipeline steps are still hardcoded.
…xt-pipeline into feat/inheritance
|
@geoo89 ran the check that we discussed in the meeting, all looks good. Vanilla crisis was still running ok so think we are safe to merge without disrupting legacy deployments. Had to add a bit of encoding detail as we discussed, also had to make some changes in the toolkit which can be seen here: IDEMSInternational/rapidpro-flow-toolkit#134 If you are happy with that, both need to be merged at the same time so can I leave that to you since I dont think I have permissions in the toolkit repo. I also added in the latest QR function as well so this should be up to date. @fagiothree the main thing to be aware of after this is merged is that to run the pipeline the command has changed from python -m parenttext_pipeline.cli to python -m parenttext_pipeline.cli pull_data compile_flows |
Repos can now reference data from other repos.
The design follows the proposal outlined here: #125
An application can be seen in the last commit of the following PR: IDEMSInternational/parenttext-crisis#51
The main thing to be aware of after this is merged is that to run the pipeline the command has changed from
python -m parenttext_pipeline.clito
python -m parenttext_pipeline.cli pull_data compile_flows